Didn't we specifically switch from a bind mount to a symlink at some point? I don't remember now :(

It was initially added here #115 because tmpfiles was deleting the file.

We removed the tmpfiles creation in #172 because microsoft changed it and it didn't merge properly.

It was added back in #207.

I think it was from the beginning a tmpfiles rule, because that is what microsoft was using at the time and it merged properly for a bit.

After a switch I got this (expected) error:

warning: the following units failed: tmp-.X11\x2dunix-X0.mount

× tmp-.X11\x2dunix-X0.mount - /tmp/.X11-unix/X0
     Loaded: loaded (/etc/fstab; generated)
     Active: failed (Result: resources)
      Where: /tmp/.X11-unix/X0
       What: /mnt/wslg/.X11-unix/X0
       Docs: man:fstab(5)
             man:systemd-fstab-generator(8)

Feb 24 16:24:20 carbon systemd[1]: tmp-.X11\x2dunix-X0.mount: Mount path /tmp/.X11-unix/X0 is not canonical (contains a symlink).
Feb 24 16:24:20 carbon systemd[1]: tmp-.X11\x2dunix-X0.mount: Failed with result 'resources'.
Feb 24 16:24:20 carbon systemd[1]: Failed to mount /tmp/.X11-unix/X0.
warning: error(s) occurred while switching to the new configuration

after a restart this went away and tmpfiles (sudo systemd-tmpfiles --clean; sudo systemd-tmpfiles --create) works as expected and now fhs envs (eg esphome through platformio) works.

Going to merge this and lets revisit it, if we overlooked something.